On the track selection screen, there are X and Y buttons next to the configuration names. Those represent the "open configuration" allowing drivers to drive around the entire track area.
Every layout file must start with the track code, e.g. BL4_something.lyt. BL4 means Blackwood Car Park. You can see the short track codes for all tracks here: https://en.lfsmanual.net/wiki/Category:Tracks
The DBL4 prefix is a mistake, it should probably be BL4_.
Now that the latest test patch provides ways to control AI cars via InSim, anyone can try and create better AI system as a challenge Although even Scawen said it's probably not suitable for creating competitive racing AI because of the input data delays and density necessary for quick reactions.
I'm wodnering, where did you find the download link in the end? It's quite surprising to me that you couldn't find the download link when there's a big button saying "FREE GAME DOWNLOAD" on the LFS home page, and a "DOWNLOADS" link as well.
Can you please upload the images as attachments instead of using a 3rd party service (Imgur)? Then they will be stored here forever and won't be removed if the Imgur goes down.
Okay, then something must be wrongly configured on my end and it's probably not a bug. Thanks, I will have another look. I have connected both my G27 and the Moza right now, maybe that could cause the issue?
When I set the wheel rotation manually in Moza Pit House software, it works perfectly as you describe. But I want LFS to automatically set the rotation for each car so I don't have to jump into MPH and adjust the rotation manually every time I change the car.
The wheel turn compensation set to 1.00 (max) makes sure the physical wheel turn always matches the in-car steering wheel, provided that the max is set to at the actual max angle or more.
Here's an exaplantion from Scawen. Point 1) applies in my case:
This worked well with my G27 - I could feel a bump stop when I reached the maximum lock angle of the given car.
For demonstration, here's a comparison of me turning the G27 wheel past its full lock and then the same with the MOZA R3. Pay attention to the FFB graph at the bottom right:
While developing an InSim app for myself, I needed to show personalised buttons to each connection and human player on track. To abstract away having to assign the button UCIDs manually, I've introduced scopes in the React Node InSim library.
Here's a demo video with two LFS users:
- the "React NodeInSim" button is the same for all connections (UCID 255)
- the username buttons are different for each connection
- the player name buttons are different for each human player on track
You can use data/script/[car name].lfs files to add /ff commands there (e.g. XRT.lfs). For mods the file must be named after the SkinID - C2EBCF.lfs for example.